Salesforce UX API icon

Salesforce UX API

(0 reviews)

TMF676- PostPaymentTowardsAria-PR

-> Create Payment from External Channel (B2BSoft & Evertec) towards Aria
URL
http://[localhost]:[port]/evertec-ux/v1/{businessId}/payment
url Param
nametypedescriptionrequired
businessIdstring2 letter ISO 3166 country code (TT, BB, JM, PA, PR, etc.) identifying the business unit.Y
namevaluedescriptionrequired
client_idstringThe client_id identifying the channel.Y
client_secretstringPassword associated with the client_id.Y
X-Correlation-IDstringIdentifier that correlates HTTP request between a client and server.
Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction.
Y
targetSystemstringTarget system value where entity need to be created , For example "Aria"Y
Request
curl --location 'https://localhost:8080/sfdc-ux/v1/PR/payment' \
--header 'client_id: f029036ffc1a4580a0143d800d206547' \
--header 'client_secret: b0ebd441fc6e4e26bcf0b73856b17328' \
--header 'X-Correlation-ID: e8c67e96-0387-4e56-82b8-e83efda9e179' \
--header 'targetSystem: Aria' \
--header 'Content-Type: application/json' \
--data-raw '{
    "@type": "invoice",
    "correlatorId": "123456707800",
    "paymentDate": "2024-10-04T00:00:00Z",
    "description": "a payment example",
    "account": {
        "id": "255853"
    },
    "amount": {
        "value": 1
    },
    "channel": {
        "id": "channel",
        "name": "EVERTEC"
    },
    "@baseType": "payment"
}'
Definitions
nametypedescriptionrequired
correlatorIdstringThis code provides a reference correlation to the external payment. This field must be unique for every payment submitted by the client.Y
paymentDatestringN
descriptionstringAdditional explanatory text relating to this API callN
accountobjectAn account referenceY
account.idstringClient-defined account identifierY
amountobjectA moneyY
amount.valuefloatThe amount of the payment being/to-be made against the outstanding account balanceY
channelobjectA channel referenceN
channel.idstringchannel idN
channel.namestringName of the channel.N
@baseTypestringBase typeN
@typestringTypeN

Possible response success

This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.

[ 200 ]

OK - createPayment request processed successfully, response body contains an entity corresponding to the requested resource.

{
    "id": "537399680",
    "@type": "invoice",
    "correlatorId": "123456707800",
    "description": "a payment example",
    "account": {
        "id": "255853"
    },
    "amount": {
        "value": 1
    },
    "channel": {
        "id": "channel",
        "name": "EVERTEC"
    },
    "@baseType": "payment"
}
Definitions
nametypedescriptionrequired
idstringThe unique identifier for a given transactionN
Appending the request with response (id)N
-> Create Payment from Internal Channel (sfdc-b2c, digital & IVR) towards Aria ( Collects or Settle the Account Balance Payment )
URL
http://[localhost]:[port]/tmf-api/paymentManagement/v4/{businessId}/payment
url Param
nametypedescriptionrequired
businessIdstring2 letter ISO 3166 country code (TT, BB, JM, PA, PR, etc.) identifying the business unit.Y
namevaluedescriptionrequired
client_idstringThe client_id identifying the channel.Y
client_secretstringPassword associated with the client_id.Y
X-Correlation-IDstringIdentifier that correlates HTTP request between a client and server.
Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction.
Y
Request
{
    "account": {
        "id": "ARIATESTING013",
        "@type": "CustomerAccountRef"
    },
    "amount": {
        "value": 22,
        "unit": "USD"
    },
    "paymentMethod": {
        "id": "SALESFORCE003_PM_019",
        "@type": "PaymentMethodRef"
    },
    "channel": {
        "id": "channel",
        "name": "SFDCB2C"
    },
    "correlatorId": "67890",
    "@type": "Payment"
}
Definitions
nametypedescriptionrequired
correlatorIdstringN
accountObjectAn account referenceY
account.idstringClient-defined account identifierY
account.@typestringAccount typeN
amountObjectA MoneyN
amount.valuefloatThe amount of money to collect from the account.N
amount.unitstringCurrencyN
paymentMethodObjectA payment method ref or valueN
paymentMethod.idstringClient-defined ID for this payment method.Y
paymentMethod.@typestringReference of paymentMethodN
channelObjectA channel referenceN
channel.idstringchannel idN
channel.namestringClient-defined unique identifier used to track related system actionsN
@typestringPayment typeN

Possible response success

This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.

[ 200 ]

OK - createPayment request processed successfully, response body contains an entity corresponding to the requested resource.

{
    "id": "1678885760.10433",
    "authorizationCode": "67890",
    "description": "509842214",
    "status": "done",
    "statusDate": "2023-03-15T13:09:20Z",
    "account": {
        "id": "ARIATESTING013",
        "@type": "CustomerAccountRef"
    },
    "amount": {
        "value": 22,
        "unit": "USD"
    },
    "paymentMethod": {
        "id": "SALESFORCE003_PM_019",
        "@type": "PaymentMethodRef"
    },
    "channel": {
        "id": "channel",
        "name": "SFDCB2C"
    },
    "correlatorId": "67890",
    "@type": "Payment"
}
Definitions
nametypedescriptionrequired
idstringThe unique identifier for a given transactionN
authorizationCodestringAuthorization code provided by the issuing bankN
descriptionstringThe unique identifier for a given transactionN
statusstringTransaction statusN
statusDatestringCurrent date, UTC formatN
Appending the request with response (id)N

Reviews